Task: Integration Test Assets Design (PD) |
| |
 |
The second activity covers the design of test assets, mainly Test Cases, Test Suites, Test Procedures and Test Scripts, the latter corresponding to integration test automation concerns. |
Disciplines: Integration Testing (PD) |
|
Purpose
Create the test assets in order to evaluate the components and modules relatioships
(interactions).
|
Main Description
The asset design is responsible for the creation of test cases, test suites, test procedures and test scripts to be futher
used during the execution phase. Information regarding to the previous performed test cycles should be considered
during this phase. |
Steps
Create tests to evaluate the component's interactions
Based on the previous activity, a test case is generated for critical paths and interactions among components in order to
evaluate if it works according to the specification. Architecture information should be considered during this step. E.g:
Architectural Views (component class diagrams, modules class diagrams, sequence diagrams, and so on) are important, since
it helps the tester to verify if the specification conforms with the code. Whereas the behavioral view provides functional
informations regarding the reference architecture, the structural view provides structural information. |
Create tests to evaluate the module's interactions
After create test cases for critical module's interactions, this integration among the module's can be performed
using an integration strategy, in order to evaluate this integration the test cases are created. The test cases
will evaluate the module's interactions based on their specification (e.g. architectural views), risks
performed during planning step.
|
Verify test coverage
Verify if the test cases or scripts created are covering the desired path. This step should be performed by
instrumentalizing the code. |
Create test scripts
Create test scripts to automatic execute the test cases. |
Create test suites
Group the tests created in the previous step according to a common objective. E.g: Group a set of test or scripts in
order to evaluate a specific feature. |
|
Key Considerations
The created assets will support execution activities. |
|